Unable to do npm install: Registry returned 401 for GET 路 Issue #12758 路 npm/npm 路 GitHub

您所在的位置：网站首页 › code e401 › Unable to do npm install: Registry returned 401 for GET 路 Issue #12758 路 npm/npm 路 GitHub

Unable to do npm install: Registry returned 401 for GET 路 Issue #12758 路 npm/npm 路 GitHub

2023-10-25 22:40| 来源: 网络整理| 查看: 265

@lxe that latter behavior (info succeeding because the metadata is cached) is known, and sort of a "lol distributed systems / cache invalidation" problem that we may or may not get around to addressing during the cache rewrite (it's sort of a footgun for users of private packages who are surprised / alarmed when they can still see packages they think they shouldn't be after they change access to their packages or dev teams).

Here's the script I was using:

mkdir test-rxjs-lol cd test-rxjs-lol/ npm init -y ~/bin/nave use 6.1.0 npm i -g [email protected] ~/bin/nave use 6.1.0 npm install rxjs-fetch --always-auth # no problems rm package.json rm -r node_modules/ npm init -y ~/bin/nave use 6.1.0 npm cache clean rxjs-fetch # being thorough, because `cache clean` doesn't remove the header metadata: rm -r ~/.npm/registry.npmjs.org/rxjs-fetch/ ~/bin/nave use 6.1.0 npm config set always-auth true ~/bin/nave use 6.1.0 npm install -S rxjs-fetch # still no problems

It could be an npm view vs npm install situation, but @scouten's problem was happening at install time.

【本文地址】

公司简介

联系我们